home *** CD-ROM | disk | FTP | other *** search
Text File | 1991-02-20 | 1.8 KB | 38 lines | [TEXT/MPS ] |
- CSHELL: Who's To Blame?
-
- First, there was Traffic-Light, and then Traffic-Light 2.0, and then
- Traffic-Light 3.0, which was a first attempt at a shell application.
- Once this was complete, I used it to write Kibitz, and from that
- experience, I learned where ShellApp feel a bit short in terms of
- being an application framework.
-
- CShell is, for the most part, Kibitz with the chess stuff ripped out.
- I did add some features to the TextEdit control for printing, sizing,
- moving, etc. I also split some source files into two, so all the code
- that the application writer would delete or change could be found in
- a single file. Other than changes like these, the application shell
- that Kibitz uses is CShell.
-
- For what can be found in which files, check out the CShell.Roadmap file.
- This will explain what is in what file, as well as what you will need to
- add or change to convert CShell from a do-hardly-anything application
- into your own application.
-
- There are some really nice things in CShell. The file I/O unit is
- reasonably robust. The printing is 7.0/AppleEvents savvy. There are a
- number of source files that you may not have to touch at all. Many
- development issues were addressed in CShell, so it can also serve as a
- good sample of the beginnings of a Macintosh application.
-
- If you don't like the overall structure, there are probably still pieces
- that you may want to use. The TextEdit control is probably one of these.
- The code is already separate from the rest of CShell. (There are no
- includes other than the standard Macintosh includes.) Take what you like
- and leave the rest. I won't be offended.
-
- We hwere in DTS are always looking to improve things, so if you find
- problems, or if you have suggestions as to how CShell can be more useful,
- let us know. We consider anything here. All suggestions are welcome.
-
- Eric Soldan
-